Automation of MLOAD and TPUMP conversion

ABSTRACT

Embodiments of the invention are directed to systems, methods and computer program products for converting MLOAD and TPUMP operations. In some embodiments, a system is configured to: receive an input production parameter, wherein the input production parameter is associated with a load utility and defines a library of parameters, wherein the library of parameters defines a first syntax; convert the first syntax of the library of parameters to a second syntax, wherein the second syntax is associated with the load utility; validate the second syntax of the library of parameters; and write an output parameter to a memory location based on positive validation of the second syntax of the library of parameters.

BACKGROUND

There is a need to enable a user to quickly and efficiently convertMLOAD and TPUMP operations.

BRIEF SUMMARY

In some embodiments, an apparatus for converting MLOAD and TPUMPoperations is provided. The apparatus comprises a memory, a processor,and a module stored in memory, executable by the processor, andconfigured to: receive an input production parameter, wherein the inputproduction parameter is associated with a load utility and defines alibrary of parameters, wherein the library of parameters defines a firstsyntax; convert the first syntax of the library of parameters to asecond syntax, wherein the second syntax is associated with the loadutility; validate the second syntax of the library of parameters; andwrite an output parameter to a memory location based on positivevalidation of the second syntax of the library of parameters.

In some embodiments, receiving the input production parameter comprisesdetermining the type of load utility.

In some embodiments, determining the type of load utility comprisescounting a number of incoming records.

In some embodiments, the load utility is MLOAD.

In some embodiments, the load utility is TPUMP.

In some embodiments, the library of parameters is stored in a database.

In some embodiments, the library of parameters is configured to beoverridden by the output parameter.

In some embodiments, the library of parameters comprises parameters.

In some embodiments, parameters comprise a Log table, a Work table, a UVtable, and an Error table.

In some embodiments, converting the first syntax of the library ofparameters comprises deleting a parameter associated with the firstsyntax.

In some embodiments, converting the first syntax of the library ofparameters comprises editing a parameter associated with the firstsyntax.

In some embodiments, converting the first syntax of the library ofparameters comprises adding a parameter associated with the secondsyntax.

In some embodiments, converting the first syntax comprises generating atleast one script and computer code of the library of the parametersusing the second syntax.

In some embodiments, validating the second syntax of the library ofparameters comprises using a compiler.

In some embodiments, validating the second syntax of the library ofparameters comprises storing the second syntax of the library ofparameters in a memory location.

In some embodiments, validating the second syntax of the library ofparameters comprises comparing the second syntax to a table stored in asecond memory location that contains syntax associated with the loadutility.

In some embodiments, writing the output parameter to a memory locationcomprises overwriting a second output parameter in the memory location.

In some embodiments, writing the output parameter to a memory locationenables the apparatus to load incoming information with the identifiedload utility.

In some embodiments, a method for converting MLOAD and TPUMP operationsis provided. The method comprises: receiving an input productionparameter, wherein the input production parameter is associated with aload utility and defines a library of parameters, wherein the library ofparameters defines a first syntax; converting the first syntax of thelibrary of parameters to a second syntax, wherein the second syntax isassociated with the load utility; validating the second syntax of thelibrary of parameters; and writing an output parameter to a memorylocation based on positive validation of the second syntax of thelibrary of parameters.

In some embodiments, a computer program product for converting MLOAD andTPUMP operations is provided. The computer program product comprises anon-transitory computer-readable medium comprising code causing acomputer to: receive an input production parameter, wherein the inputproduction parameter is associated with a load utility and defines alibrary of parameters, wherein the library of parameters defines a firstsyntax; convert the first syntax of the library of parameters to asecond syntax, wherein the second syntax is associated with the loadutility; validate the second syntax of the library of parameters; andwrite an output parameter to a memory location based on positivevalidation of the second syntax of the library of parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, where:

FIG. 1 is a general process flow for identifying a load utility;

FIG. 2 is an exemplary user interface for converting MLOAD and TPUMPoperations, in accordance with embodiments of the present invention;

FIG. 3 is a block diagram illustrating technical components of a systemfor converting MLOAD and TPUMP operations, in accordance withembodiments of the present invention; and

FIG. 4 is a block diagram illustrating the automated process ofconverting a load utility.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention now may be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure may satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

In some embodiments, an “entity” as used herein may be a financialinstitution. For the purposes of this invention, a “financialinstitution” may be defined as any organization, entity, or the like inthe business of moving, investing, or lending money, dealing infinancial instruments, or providing financial services. This may includecommercial banks, thrifts, federal and state savings banks, savings andloan associations, credit unions, investment companies, insurancecompanies and the like. In some embodiments, the entity may allow a userto establish an account with the entity. An “account” may be therelationship that the user has with the entity. Examples of accountsinclude a deposit account, such as a transactional account (e.g. abanking account), a savings account, an investment account, a moneymarket account, a time deposit, a demand deposit, a pre-paid account, acredit account, a non-monetary user profile that includes only personalinformation associated with the user, or the like. The account isassociated with and/or maintained by an entity. In other embodiments, an“entity” may not be a financial institution.

In some embodiments, a “user” may be an agent (customer servicerepresentative, internal operations specialist, bank teller, accountmanager, IT technician, database manager, mainframe operator, or thelike) associated with the entity. The user may also be a customer (e.g.an account holder or a person who has an account (e.g. banking account,credit account, or the like) at the entity) or a merchant (e.g. abusiness, a vendor, a service provider, or the like).

The present invention may enable an apparatus (e.g. a computer system)associated with the entity to efficiently load incoming information(entries in a CSV file, data, metadata, or the like) into a database (amainframe, a datastore, a memory location, a table, or the like). Theapparatus may dynamically load incoming information into a database viatwo different load utilities, namely MLOAD (a Teradata “multiload” loadutility) and TPUMP (a Teradata load utility that does not lock tables).Generally speaking, the apparatus may utilize the MLOAD load utility forlarger volumes of information while the TPUMP load utility may beutilized for smaller volumes of incoming information. Therefore, MLOADtypically uses more computer resources than TPUMP.

The entity's current database management system may require the user tomanually determine which load utility is appropriate to use for a volumeof incoming information. The user may be required to manually switchbetween the two load utilities. These manual processes may often requirewriting computer code and thus may be time consuming and laborious.Furthermore, using the MLOAD load utility for a small volume of incominginformation may be a costly and inefficient use of computer resources.

The present invention may include an automated system for determiningthe appropriate load utility. The appropriate load utility may bedetermined based on the volume of incoming information. Once theappropriate load utility has been determined, the present invention maybe configured to automatically switch between the two load utilities toensure that the apparatus is loading the incoming information with theappropriate load utility. Automating these two processes may betterallocate computer resources and thus save the entity time and money.

First, the apparatus may receive at least one input productionparameter. The at least one input production parameter may includeincoming information (information associated with a transaction,information associated with an account, or the like). The at least oneinput production parameter may be used to identify the type, the size,or the volume of the incoming information.

The apparatus may analyze the at least one input production parameter todetermine the volume of incoming information. In some embodiments, theapparatus may utilize a counter or an ICETOOL (a utility that counts orsorts information) to count the number of pieces of incoming informationassociated with the at least one input production parameter. In someembodiments, the count of pieces of incoming information associated withthe at least one input production parameter may be stored in memory. Inother embodiments, the count of pieces of incoming informationassociated with the at least one input production parameter may becompared to a predetermined threshold value. This threshold value maydefine a cutoff value for determining the appropriate load utility.Comparing the count of pieces of incoming information associated withthe at least one input production parameter to the threshold value maycreate one of three potential cases.

In some embodiments, the count of pieces of incoming informationassociated with the at least one input production parameter may be lessthan the predetermined threshold value. A count of pieces of incominginformation associated with the at least one input production parameterthat is less than the predetermined threshold value may suggest thatthere is a smaller volume of incoming information. So, the apparatus mayautomatically configure the system to load the incoming informationusing the TPUMP load utility. This configuration may save computerresources by using TPUMP, the load utility that requires less computerresources.

In other embodiments, the count of pieces of incoming informationassociated with the at least one input production parameter may begreater than the predetermined threshold value. A count of pieces ofincoming information associated with the at least one input productionparameter that is greater than the predetermined threshold value maysuggest that there is a larger volume of incoming information. So, theapparatus may automatically configure the system to load the incominginformation using the MLOAD load utility. While this configuration mayuse more computer resources, using the MLOAD load utility may ensurethat the larger volume of incoming information is efficiently andaccurately loaded into the database.

In alternative embodiments, the count of pieces of incoming informationassociated with the at least one input production parameter may be equalto the predetermined threshold value. Hence, the apparatus may beconfigured to load the incoming information using either of the two loadutilities. The entity may reserve the right to determine which loadutility to use when the counted number of pieces of incoming informationis found to be equal to the predetermined threshold value. For example,if the entity is focused on saving computer resources, TPUMP may be usedto input the incoming information into the database. Conversely, if theentity is focused on accuracy when loading incoming information, MLOADmay be used to input the incoming information into the database.

Once the appropriate load utility is determined, the apparatus may beconfigured to automatically convert the database management system tothe appropriate load utility. The apparatus may first determine if thesystem is already configured with the appropriate type of load utility.For example, if the previous input production parameter required use ofthe MLOAD load utility and the present input production parameterrequires the MLOAD load utility, then no conversion may be necessary.Conversely, if the previous input production parameter required use ofthe MLOAD load utility and the present input production parameterrequires the TPUMP load utility, then a conversion may be necessary.

To convert the database management system to the appropriate loadutility, the apparatus may automatically retrieve a library ofparameters associated with the determined appropriate load utility. Theapparatus may then analyze the library of parameters to locateparameters (a Log table, a UV table, a Work table, an Error table, orthe like) that are not associated with the determined appropriateutility. If any unassociated parameters are found, the apparatus mayautomatically delete the unassociated parameters from the library ofparameters.

For example, if the MLOAD load utility is determined to be theappropriate load utility and the apparatus locates TPUMP-relatedparameters in the library of parameters, the apparatus may automaticallydelete the TPUMP-related parameters. Conversely, if the TPUMP loadutility is determined to be the appropriate load utility and theapparatus locates MLOAD-related parameters in the library of parameters,the apparatus may automatically delete the MLOAD-related parameters.

In other embodiments, the apparatus may not delete the unassociatedparameters, but may flag them or edit them to comply with the syntax ofthe appropriate load utility. The apparatus may automatically change,add, or edit parameters in accordance with the syntax associated withthe determined appropriate load utility. For example, if the MLOAD loadutility is determined to be the appropriate load utility for the presentinput production parameter, the apparatus may automatically add astatement, a parameter, or the like into the library of parameters inaccordance with the syntax associated with the MLOAD load utility.Conversely, if the TPUMP load utility is determined to be theappropriate load utility for the present input production parameter, theapparatus may automatically add statements, parameters, or the like intothe library of parameters in accordance with the syntax associated withthe TPUMP load utility. This process may ensure that the library ofparameters contains statements that are executable in the conversionprocess.

Once the library of parameters is converted into the appropriate syntaxby the apparatus, the apparatus may validate the library of parameters(or a script, computer code, or the like associated with the library ofparameters). In some embodiments, the apparatus may utilize a compileror similar software to verify that the library of parameters containsthe appropriate syntax and that all aspects of the library of parametersare executable.

In some embodiments, the apparatus may automatically overwrite aprevious library of parameters with the library of parameters associatedwith the present incoming information. This process is meant to ensurethat the library of parameters associated with the present incominginformation is used to input the incoming information. In otherembodiments, the apparatus may overwrite the previous library ofparameters with the library of parameters associated with the presentincoming information in a specific memory location. In alternativeembodiments, the apparatus may override the library of parameters withthe library of parameters associated with the present incominginformation and output the present library of parameters to a secondapparatus in the database management system.

Next, the apparatus may begin to input the incoming information into thedatabase using the determined appropriate load utility. The incominginformation may be stored in the database for a predetermined period oftime or in a predetermined storage location. The entity may reserve theright to determine the period of time during which the incominginformation may be stored as well as the storage location.

FIG. 1 illustrates a general process flow 100 for identifying the loadutility, either MLOAD or TPUMP. At block 110 the process includesreceiving a first information, wherein the first information comprisesat least one piece of data. At block 120 the process includes countingthe number of pieces of data. At block 130 the process includescomparing the counted number of pieces of data to a predeterminedthreshold value. At block 140 the process includes identifying a loadutility based on the comparison between the counted number of pieces ofdata and the predetermined threshold value.

FIG. 2 illustrates a general process flow 200 for dynamically convertinga database management system between two load utilities, namely MLOADand TPUMP. At block 210 the process includes receiving an inputproduction parameter, wherein the input production parameter isassociated with a load utility and defines a library of parameters,wherein the library of parameters defines a first syntax. At block 220the process includes converting the first syntax of the library ofparameters to a second syntax, wherein the second syntax is associatedwith the load utility. At block 230 the process includes validating thesecond syntax of the library of parameters. At block 240 the processincludes writing an output parameter to a memory location based onpositive validation of the second syntax of the library of parameters.

FIG. 3 presents an exemplary block diagram of the system environment 300for implementing the process flow described in FIGS. 1 and 2 inaccordance with embodiments of the present invention. As illustrated,the system environment 300 includes a network 310, a system 330, and auser input system 340. Also shown in FIG. 3 is a user 345 of the userinput system 340. The user input system 340 may be a mobile devicedescribed herein. The user 345 may be a person who uses the user inputsystem 340 to execute a user application 347. The user application 347may be an application to communicate with the system 330, perform atransaction, input information onto a user interface presented on theuser input system 340, or the like. The user application 347 and/or thesystem application 337 may incorporate one or more parts of any processflow described herein.

As shown in FIG. 3, the system 330, and the user input system 340 areeach operatively and selectively connected to the network 310, which mayinclude one or more separate networks. In addition, the network 310 mayinclude a telecommunication network, local area network (LAN), a widearea network (WAN), and/or a global area network (GAN), such as theInternet. It will also be understood that the network 310 may be secureand/or unsecure and may also include wireless and/or wireline and/oroptical interconnection technology.

The user input system 340 may include any computerized apparatus thatcan be configured to perform any one or more of the functions of theuser input system 340 described and/or contemplated herein. For example,the user 345 may use the user input system 340 to transmit and/orreceive information or commands to and from the system 330. In someembodiments, for example, the user input system 340 may include apersonal computer system (e.g. a non-mobile or non-portable computingsystem, a motor vehicle, or the like), a mobile computing device, apersonal digital assistant, a mobile phone, a tablet computing device, anetwork device, and/or the like. As illustrated in FIG. 3, in accordancewith some embodiments of the present invention, the user input system340 includes a communication interface 342, a processor 344, a memory346 having an user application 347 stored therein, and a user interface349. In such embodiments, the communication interface 342 is operativelyand selectively connected to the processor 344, which is operatively andselectively connected to the user interface 349 and the memory 346. Insome embodiments, the user 345 may use the user application 347 toexecute processes described with respect to the process flows describedherein. Specifically, the user application 347 executes the process flowdescribed in FIG. 1.

Each communication interface described herein, including thecommunication interface 342, generally includes hardware, and, in someinstances, software, that enables the user input system 340, totransport, send, receive, and/or otherwise communicate information toand/or from the communication interface of one or more other systems onthe network 310. For example, the communication interface 342 of theuser input system 340 may include a wireless transceiver, modem, server,electrical connection, and/or other electronic device that operativelyconnects the user input system 340 to another system such as the system330. The wireless transceiver may include a radio circuit to enablewireless transmission and reception of information. Additionally, theuser input system 340 may include a positioning system. The positioningsystem (e.g. a global positioning system (GPS), a network address (IPaddress) positioning system, a positioning system based on the nearestcell tower location, or the like) may enable at least one of the userinput system 340 or an external server or computing device incommunication with the user input system 340 to determine the location(e.g. location coordinates) of the user input system 340.

Each processor described herein, including the processor 344, generallyincludes circuitry for implementing the audio, visual, and/or logicfunctions of the user input system 340. For example, the processor mayinclude a digital signal processor device, a microprocessor device, andvarious analog-to-digital converters, digital-to-analog converters, andother support circuits. Control and signal processing functions of thesystem in which the processor resides may be allocated between thesedevices according to their respective capabilities. The processor mayalso include functionality to operate one or more software programsbased at least partially on computer-executable program code portionsthereof, which may be stored, for example, in a memory device, such asin the user application 347 of the memory 346 of the user input system340.

Each memory device described herein, including the memory 346 forstoring the user application 347 and other information, may include anycomputer-readable medium. For example, memory may include volatilememory, such as volatile random access memory (RAM) having a cache areafor the temporary storage of information. Memory may also includenon-volatile memory, which may be embedded and/or may be removable. Thenon-volatile memory may additionally or alternatively include an EEPROM,flash memory, and/or the like. The memory may store any one or more ofpieces of information and data used by the system in which it resides toimplement the functions of that system.

As shown in FIG. 3, the memory 346 includes the user application 347.The user application 347 may be associated with various features of thedevice identification program. In some embodiments, the user application347 includes an interface for communicating with, navigating,controlling, configuring, and/or using the user input system 340. Insome embodiments, the user application 347 includes computer-executableprogram code portions for instructing the processor 344 to perform oneor more of the functions of the user application 347 described and/orcontemplated herein. In some embodiments, the user application 347 mayinclude and/or use one or more network and/or system communicationprotocols.

Also shown in FIG. 3 is the user interface 349. In some embodiments, theuser interface 349 includes one or more output devices, such as adisplay and/or speaker, for presenting information to the user 345. Insome embodiments, the user interface 349 includes one or more inputdevices, such as one or more buttons, keys, dials, levers, directionalpads, joysticks, accelerometers, controllers, microphones, touchpads,touchscreens, haptic interfaces, microphones, scanners, motiondetectors, cameras, and/or the like for receiving information from theuser 345. In some embodiments, the user interface 349 includes the inputand display devices of a mobile device, which are operable to receiveand display information.

FIG. 3 also illustrates a system 330, in accordance with an embodimentof the present invention. The system 330 may refer to the “apparatus”described herein. The system 330 may include any computerized apparatusthat can be configured to perform any one or more of the functions ofthe system 330 described and/or contemplated herein. In accordance withsome embodiments, for example, the system 330 may include a computernetwork, an engine, a platform, a server, a database system, a front endsystem, a back end system, a personal computer system, and/or the like.Therefore, the system 330 may be a server managed by the entity. Thesystem 330 may be located at the facility associated with the entity orremotely from the facility associated with the entity. In someembodiments, such as the one illustrated in FIG. 3, the system 330includes a communication interface 332, a processor 334, and a memory336, which includes a system application 337 and a datastore 338 storedtherein. As shown, the communication interface 332 is operatively andselectively connected to the processor 334, which is operatively andselectively connected to the memory 336.

It will be understood that the system application 337 may be configuredto implement any one or more portions of the various user interfacesand/or process flow described herein. The system application 337 mayinteract with the user application 347. It will also be understood that,in some embodiments, the memory includes other applications. It willalso be understood that, in some embodiments, the system application 337is configured to communicate with the datastore 338, the user inputsystem 340, or the like.

It will be further understood that, in some embodiments, the systemapplication 337 includes computer-executable program code portions forinstructing the processor 334 to perform any one or more of thefunctions of the system application 337 described and/or contemplatedherein. In some embodiments, the system application 337 may includeand/or use one or more network and/or system communication protocols.

In addition to the system application 337, the memory 336 also includesthe datastore 338. As used herein, the datastore 338 may be one or moredistinct and/or remote datastores. In some embodiments, the datastore338 is not located within the system and is instead located remotelyfrom the system. In some embodiments, the datastore 338 storesinformation or data described herein. For example, the datastore 338 maystore information associated with the user's account.

It will be understood that the datastore 338 may include any one or morestorage devices, including, but not limited to, datastores, databases,and/or any of the other storage devices typically associated with acomputer system. It will also be understood that the datastore 338 maystore information in any known way, such as, for example, by using oneor more computer codes and/or languages, alphanumeric character strings,data sets, figures, tables, charts, links, documents, and/or the like.Further, in some embodiments, the datastore 338 may include informationassociated with one or more applications, such as, for example, thesystem application 337. It will also be understood that, in someembodiments, the datastore 338 provides a substantially real-timerepresentation of the information stored therein, so that, for example,when the processor 334 accesses the datastore 338, the informationstored therein is current or substantially current.

It will be understood that the embodiment of the system environmentillustrated in FIG. 3 is exemplary and that other embodiments may vary.As another example, in some embodiments, the system 330 includes more,less, or different components. As another example, in some embodiments,some or all of the portions of the system environment 300 may becombined into a single portion. Likewise, in some embodiments, some orall of the portions of the system 330 may be separated into two or moredistinct portions.

In addition, the various portions of the system environment 300 may bemaintained for and/or by the same or separate parties. It will also beunderstood that the system 330 may include and/or implement anyembodiment of the present invention described and/or contemplatedherein. For example, in some embodiments, the system 330 is configuredto implement any one or more of the embodiments of the process flowsdescribed and/or contemplated herein in connection any process flowdescribed herein. Additionally, the system 330 or the user input system340 is configured to initiate presentation of any of the user interfacesdescribed herein.

FIG. 4 depicts the automated process 400 for converting a load utility.As described in detail above, the process 400 includes receiving aninput (an input production parameter, incoming information, or the like)at block 410. Processing the input at block 420 includes determining thetype of input (whether it requires MLOAD or TPUMP), editing the syntaxof the library of parameters according to the determined type of input,validating the script, and writing the code to override the library ofparameters. At block 430, the output includes overriding the library ofparameters.

In accordance with embodiments of the invention, the term “module” withrespect to a system may refer to a hardware component of the system, asoftware component of the system, or a component of the system thatincludes both hardware and software. As used herein, a module mayinclude one or more modules, where each module may reside in separatepieces of hardware or software.

Although many embodiments of the present invention have just beendescribed above, the present invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Also, it will beunderstood that, where possible, any of the advantages, features,functions, devices, and/or operational aspects of any of the embodimentsof the present invention described and/or contemplated herein may beincluded in any of the other embodiments of the present inventiondescribed and/or contemplated herein, and/or vice versa. In addition,where possible, any terms expressed in the singular form herein aremeant to also include the plural form and/or vice versa, unlessexplicitly stated otherwise. Accordingly, the terms “a” and/or “an”shall mean “one or more,” even though the phrase “one or more” is alsoused herein. Like numbers refer to like elements throughout.

As will be appreciated by one of ordinary skill in the art in view ofthis disclosure, the present invention may include and/or be embodied asan apparatus (including, for example, a system, machine, device,computer program product, and/or the like), as a method (including, forexample, a business method, computer-implemented process, and/or thelike), or as any combination of the foregoing. Accordingly, embodimentsof the present invention may take the form of an entirely businessmethod embodiment, an entirely software embodiment (including firmware,resident software, micro-code, stored procedures in a database, or thelike), an entirely hardware embodiment, or an embodiment combiningbusiness method, software, and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product thatincludes a computer-readable storage medium having one or morecomputer-executable program code portions stored therein. As usedherein, a processor, which may include one or more processors, may be“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing one or more computer-executableprogram code portions embodied in a computer-readable medium, and/or byhaving one or more application-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, electromagnetic, infrared, and/orsemiconductor system, device, and/or other apparatus. For example, insome embodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as, forexample, a propagation signal including computer-executable program codeportions embodied therein.

One or more computer-executable program code portions for carrying outoperations of the present invention may include object-oriented,scripted, and/or unscripted programming languages, such as, for example,Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript,and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F#.

Some embodiments of the present invention are described herein withreference to flowchart illustrations and/or block diagrams of apparatusand/or methods. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and/or combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions. These one or more computer-executable program code portionsmay be provided to a processor of a general purpose computer, specialpurpose computer, and/or some other programmable data processingapparatus in order to produce a particular machine, such that the one ormore computer-executable program code portions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, create mechanisms for implementing the steps and/or functionsrepresented by the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may be storedin a transitory and/or non-transitory computer-readable medium (e.g. amemory) that can direct, instruct, and/or cause a computer and/or otherprogrammable data processing apparatus to function in a particularmanner, such that the computer-executable program code portions storedin the computer-readable medium produce an article of manufactureincluding instruction mechanisms which implement the steps and/orfunctions specified in the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with, and/or replaced with,operator- and/or human-implemented steps in order to carry out anembodiment of the present invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, modifications, andcombinations of the just described embodiments can be configured withoutdeparting from the scope and spirit of the invention. Therefore, it isto be understood that, within the scope of the appended claims, theinvention may be practiced other than as specifically described herein.

What is claimed is:
 1. An apparatus for converting MLOAD and TPUMPoperations, the apparatus comprising: a memory; at least one processor;and a module stored in the memory, wherein said module comprisingcomputer instruction code executable by the at least one processor, andstructured to cause said at least one processor to: electronicallyreceive an input production parameter, wherein the input productionparameter is associated with a load utility and defines a library ofparameters, wherein the input production parameter comprises one or morerecords, wherein the library of parameters defines a first syntax,wherein the library of parameters comprise a Log table, a Work table, aUniqueness Violation (UV) table, and/or an Error table; count the numberof records in the input production parameter; compare the counted numberof records to a predetermined threshold value; identify the load utilityto be used to load the records into a database based on the comparisonbetween the counted number of records and the predetermined thresholdvalue, wherein identifying further comprises (i) determining that thenumber of records is greater than the predetermined threshold, andloading the input production parameter into a database using a multiloadload utility (MLOAD); or (ii) determining that the number of records isless than the predetermined threshold, and loading the input productionparameter into the database using a Teradata load utility (TPUMP),whereby larger volumes of records are processed during the MLOAD loadutility and smaller volumes of records are processed using the TPUMPutility, and whereby less computer resources are used to implement TPUMPthan MLOAD thereby providing for conservation of computer resources;load the input production parameter into the database, wherein loadingfurther comprises switching the loading of the input productionparameter into the database between the MLOAD load utility and the TPUMPutility based on at least comparing the counted number of records to thepredetermined threshold value; convert the first syntax of the libraryof parameters to a second syntax, wherein the second syntax isassociated with the identified load utility, wherein converting thefirst syntax comprises generating at least one script and computer codeof the library of the parameters using the second syntax, whereinconverting further comprises: identifying one or more unassociatedparameters, wherein the one or more unassociated parameters are notassociated with the identified load utility; automatically editing theone or more unassociated parameters to comply with the second syntax,wherein automatically editing further comprises automatically adding astatement and a parameter into the library of parameters associated withthe identified load utility; and updating the library of parametersbased on at least automatically editing the one or more unassociatedparameters, wherein updating further comprises overwriting the libraryof parameters; validate the second syntax of the library of parameters,wherein validating the second syntax of the library of parameterscomprises using a compiler; and write an output parameter to a memorylocation based on positive validation of the second syntax of thelibrary of parameters.
 2. The apparatus of claim 1, wherein receivingthe input production parameter comprises determining the type of loadutility.
 3. The apparatus of claim 1, wherein the library of parametersis stored in a database.
 4. The apparatus of claim 1, wherein thelibrary of parameters is configured to be overridden by the outputparameter.
 5. The apparatus of claim 1, wherein converting the firstsyntax of the library of parameters comprises deleting a parameterassociated with the first syntax.
 6. The apparatus of claim 1, whereinvalidating the second syntax of the library of parameters comprisesstoring the second syntax of the library of parameters in a memorylocation.
 7. The apparatus of claim 1, wherein validating the secondsyntax of the library of parameters comprises comparing the secondsyntax to a table stored in a second memory location that containssyntax associated with the load utility.
 8. The apparatus of claim 1,wherein writing the output parameter to a memory location comprisesoverwriting a second output parameter in the memory location.
 9. Theapparatus of claim 1, wherein writing the output parameter to a memorylocation enables the apparatus to load incoming information with theidentified load utility.
 10. A method for converting MLOAD and TPUMPoperations, the method comprising: electronically receiving an inputproduction parameter, wherein the input production parameter isassociated with a load utility and defines a library of parameters,wherein the input production parameter comprises one or more records,wherein the library of parameters defines a first syntax, wherein thelibrary of parameters comprise a Log table, a Work table, a UniquenessViolation (UV) table, and/or an Error table; counting the number ofrecords in the input production parameter; comparing the counted numberof records to a predetermined threshold value; identifying the loadutility to be used to load the records into a database based on thecomparison between the counted number of records and the predeterminedthreshold value, wherein identifying further comprises (i) determiningthat the number of records is greater than the predetermined threshold,and loading the input production parameter into a database using amultiload load utility (MLOAD); or (ii) determining that the number ofrecords is less than the predetermined threshold, and loading the inputproduction parameter into the database using a Teradata load utility(TPUMP), whereby larger volumes of records are processed during theMLOAD load utility and smaller volumes of records are processed usingthe TPUMP utility, and whereby less computer resources are used toimplement TPUMP than MLOAD thereby providing for conservation ofcomputer resources; loading the input production parameter into thedatabase, wherein loading further comprises switching the loading of theinput production parameter into the database between the MLOAD loadutility and the TPUMP utility based on at least comparing the countednumber of records to the predetermined threshold value; converting thefirst syntax of the library of parameters to a second syntax, whereinthe second syntax is associated with the identified load utility,wherein converting the first syntax comprises generating at least onescript and computer code of the library of the parameters using thesecond syntax, wherein converting further comprises: identifying one ormore unassociated parameters, wherein the one or more unassociatedparameters are not associated with the identified load utility;automatically editing the one or more unassociated parameters to complywith the second syntax, wherein automatically editing further comprisesautomatically adding a statement and a parameter into the library ofparameters associated with the identified load utility; and updating thelibrary of parameters based on at least automatically editing the one ormore unassociated parameters, wherein updating further comprisesoverwriting the library of parameters; validating the second syntax ofthe library of parameters, wherein validating the second syntax of thelibrary of parameters comprises using a compiler; and writing an outputparameter to a memory location based on positive validation of thesecond syntax of the library of parameters.
 11. A computer programproduct for converting MLOAD and TPUMP operations, the computer programproduct comprising a non-transitory computer-readable medium comprisingcode causing a computer to: electronically receive an input productionparameter, wherein the input production parameter is associated with aload utility and defines a library of parameters, wherein the inputproduction parameter comprises one or more records, wherein the libraryof parameters defines a first syntax, wherein the library of parameterscomprise a Log table, a Work table, a Uniqueness Violation (UV) table,and/or an Error table; count the number of records in the inputproduction parameter; compare the counted number of records to apredetermined threshold value; identify the load utility to be used toload the records into a database based on the comparison between thecounted number of records and the predetermined threshold value, whereinidentifying further comprises (i) determining that the number of recordsis greater than the predetermined threshold, and loading the inputproduction parameter into a database using a multiload load utility(MLOAD); or (ii) determining that the number of records is less than thepredetermined threshold, and loading the input production parameter intothe database using a Teradata load utility (TPUMP), whereby largervolumes of records are processed during the MLOAD load utility andsmaller volumes of records are processed using the TPUMP utility, andwhereby less computer resources are used to implement TPUMP than MLOADthereby providing for conservation of computer resources; load the inputproduction parameter into the database, wherein loading furthercomprises switching the loading of the input production parameter intothe database between the MLOAD load utility and the TPUMP utility basedon at least comparing the counted number of records to the predeterminedthreshold value; convert the first syntax of the library of parametersto a second syntax, wherein the second syntax is associated with theidentified load utility, wherein converting the first syntax comprisesgenerating at least one script and computer code of the library of theparameters using the second syntax, wherein converting furthercomprises: identifying one or more unassociated parameters, wherein theone or more unassociated parameters are not associated with theidentified load utility; automatically editing the one or moreunassociated parameters to comply with the second syntax, whereinautomatically editing further comprises automatically adding a statementand a parameter into the library of parameters associated with theidentified load utility; and updating the library of parameters based onat least automatically editing the one or more unassociated parameters,wherein updating further comprises overwriting the library ofparameters; validate the second syntax of the library of parameters,wherein validating the second syntax of the library of parameterscomprises using a compiler; and write an output parameter to a memorylocation based on positive validation of the second syntax of thelibrary of parameters.